Server Cannot be Found


      This topic addresses those instances where, when attempting to launch the Knowledge Builder, an error message is displayed indicating the connection to the Knowledge Builder Server could not be found or established.

      This error may be displayed:
      • During Knowledge Builder startup, which prevents the Knowledge Builder Client from running. Refer to Server Connection Fails During KB Startup for more information.

      • When the user attempts to perform any Knowledge Builder Client related operation (e.g. navigate TreeView) that requires access of the KB Server. The running Knowledge Builder Client will not close in this scenario, but will continue to display an error message each time such an operation is attempted. Refer to Server Connection Fails During KB Run-Time for more information.

    Server Connection Fails During KB Startup


      If the KB Server location has become inaccessible, and an attempt is made to launch the Knowledge Builder Client, then a "Knowledge Builder unable to access to defined Server" error message is displayed.

      The Knowledge Builder Client will not launch if it cannot locate the targeted server location during initialization.

      The following table associates the specific Knowledge Builder Client/Server configuration with this error and provides possible causes and actions.

      Client/Server Configuration

      Possible Cause

      Action

      The KB Client is known to be targeting the local computer CD-ROM drive as its current KB Server.

      The local computer CD-ROM drive failed or failed to initialize.

      Troubleshoot and, if necessary, replace the CD-ROM drive.

      The local computer CD-ROM drive no longer contains the KB CD-ROM disk.

      Insert a KB CD-ROM in the local computer's CD-ROM drive.

      The local computer CD-ROM drive contains a damaged KB CD-ROM disk.

      Repair or replace the KB CD-ROM disk.

      The KB Client is known to be targeting the local computer hard disk drive as its current KB Server.

      The local computer hard disk drive targeted by the KB Client has failed or been removed.

      Troubleshoot and, if necessary, replace the hard drive.
      Reinstall the KB Server (all necessary booksets).

      The KB Server has been uninstalled from the targeted local computer had disk drive.

      Reinstall the KB Server (all necessary booksets).

      The KB Client is targeting a Server path where the path has been corrupted.

      The KB Client is known to be targeting a remote networked computer as its current KB Server.

      The network may be down between the KB Client and targeted Server location.

      Perform either of the following:

      • Troubleshoot and correct any network or server problems.
       

      The targeted KB Server may be offline or has failed.

      • If remote computer is connected to the network and the KB Server location was targeting a:
        • CD-ROM drive on the remote, networked computer, then insert a KB CD-ROM drive.
      • Troubleshoot and, if necessary, replace the hard drive and reinstall the KB Server (all necessary booksets).

    Server Connection Fails During KB Run-Time


      The Knowledge Builder Client will not shutdown if it loses the connection to its targeted server location during initialization. However, any attempt to execute a KB Client function that requires KB Server access, will display a "Knowledge Builder unable to access to defined Server" error message.

      The following table associates the specific Knowledge Builder Client/Server configuration with this error and provides possible causes and actions.

      Client/Server Configuration

      Possible Cause

      Action

      The KB Client is known to be targeting the local computer CD-ROM drive as its current KB Server.

      The local computer CD-ROM drive failed or failed to initialize.

      Perform either of the following:

      • Troubleshoot and, if necessary, replace the CD-ROM drive.
      • Use the Knowledge Builder Administration Utility to redirect the client's KB Server connection to the previous KB server location.

      The local computer CD-ROM drive no longer contains the KB CD-ROM disk.

      Perform either of the following:

      • Insert a KB CD-ROM in the local computer's CD-ROM drive.
      • Use the Knowledge Builder Administration Utility to redirect the client's KB Server connection to the previous KB server location.

      The local computer CD-ROM drive contains a damaged KB CD-ROM disk.

      Perform either of the following:

      • Repair or replace the KB CD-ROM disk.
      • Use the Knowledge Builder Administration Utility to redirect the client's KB Server connection to the previous KB server location.

      The KB Client is known to be targeting the local computer hard disk drive as its current KB Server.

      The local computer hard disk drive targeted by the KB Client has failed or been removed.

      Perform any of the following:

      • Troubleshoot and, if necessary, replace the hard drive.
      • Reinstall the KB Server (all necessary booksets).
      • Use the Knowledge Builder Administration Utility to redirect the client's KB Server connection to the previous KB server location.

      The KB Server has been uninstalled from the targeted local computer had disk drive.

      Perform either of the following:

      • Reinstall the KB Server (all necessary booksets).
      • Use the Knowledge Builder Administration Utility to redirect the client's KB Server connection to the previous KB server location.

      The KB Client is targeting a Server path where the path has been corrupted.

      The KB Client is known to be targeting a remote networked computer as its current KB Server.

      The network may be down between the KB Client and targeted Server location.

      Perform either of the following:

      • Troubleshoot and repair the network problem.
      • Use the Knowledge Builder Administration Utility to redirect the client's KB Server connection to the previous KB server location.

      The targeted KB Server may be offline or has failed.